Aerial vehicle delivery of items available through an e-commerce shopping site

ABSTRACT

This disclosure describes an unmanned aerial vehicle (“UAV”) configured to autonomously deliver items of inventory to various destinations. The UAV may receive inventory information and a destination location and autonomously retrieve the inventory from a location within a materials handling facility, compute a route from the materials handling facility to a destination and travel to the destination to deliver the inventory.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. Utility application Ser. No.14/502,707, filed Sep. 30, 2014, entitled “Unmanned Aerial VehicleDelivery System,” claims priority to U.S. Provisional Application61/896,065, filed Oct. 26, 2013, entitled “Automated Aerial DeliveryVehicle,” and U.S. Provisional Application 61/901,431, filed Nov. 7,2013, entitled “Automated Aerial Delivery Vehicle Routine And Safety,”all of which are incorporated herein by reference in their entirety.

BACKGROUND

Physical delivery of items to user specified locations has improveddramatically over the years, with some retailers offering next daydelivery of ordered items. The final, or last mile delivery of physicalitems to a user specified location is traditionally accomplished using ahuman controlled truck, bicycle, cart, etc. For example, a user mayorder an item for delivery to their home. The item may be picked from amaterials handling facility, packed and shipped to the customer forfinal delivery by a shipping carrier. The shipping carrier will load theitem onto a truck that is driven by a human to the final deliverylocation and the human driver, or another human companion with thedriver, will retrieve the item from the truck and complete the deliveryto the destination. For example, the human may hand the item to arecipient, place the item on the user's porch, store the item in a postoffice box, etc.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical components or features.

FIG. 1 depicts a graphical user interface for selecting a deliveryoption for the delivery of an item, in an implementation.

FIG. 2 depicts a block diagram of a top-down view of an unmanned aerialvehicle, according to an implementation.

FIGS. 3A-3G depict block diagrams of various inventory engagementmechanisms for engaging and disengaging inventory handled by theunmanned aerial vehicle illustrated in FIG. 2, according to animplementation.

FIG. 4 depicts a block diagram of a secure delivery location, accordingto an implementation.

FIG. 5 depicts a diagram of a UAV environment, according to animplementation.

FIG. 6 depicts a block diagram of a UAV landing at an attended deliverylocation, according to an implementation.

FIG. 7 is a flow diagram illustrating an example process for presentingan unmanned aerial vehicle delivery option for an item, according to animplementation.

FIG. 8 is a flow diagram illustrating an example aerial deliveryplanning process, according to an implementation.

FIG. 9 is a flow diagram illustrating an example automated aerialdelivery process, according to an implementation.

FIG. 10 is a flow diagram illustrating an example unmanned aerialvehicle route planning process, according to an implementation.

FIG. 11 is a flow diagram illustrating an example route navigationprocess, according to an implementation.

FIG. 12 is a flow diagram illustrating an example delivery notificationprocess, according to an implementation.

FIG. 13 is a flow diagram illustrating an example unmanned aerialvehicle landing process, according to an implementation.

FIG. 14 is a block diagram illustrating various components of anunmanned aerial vehicle control system, according to an implementation.

FIG. 15 is a block diagram of an illustrative implementation of a serversystem that may be used with various implementations.

While implementations are described herein by way of example, thoseskilled in the art will recognize that the implementations are notlimited to the examples or drawings described. It should be understoodthat the drawings and detailed description thereto are not intended tolimit implementations to the particular form disclosed but, on thecontrary, the intention is to cover all modifications, equivalents andalternatives falling within the spirit and scope as defined by theappended claims. The headings used herein are for organizationalpurposes only and are not meant to be used to limit the scope of thedescription or the claims. As used throughout this application, the word“may” is used in a permissive sense (i.e., meaning having the potentialto), rather than the mandatory sense (i.e., meaning must). Similarly,the words “include,” “including,” and “includes” mean including, but notlimited to.

DETAILED DESCRIPTION

This disclosure describes an unmanned aerial vehicle (“UAV”) configuredto autonomously deliver items of inventory to various deliverylocations. As discussed in further detail below, in someimplementations, the UAV may receive delivery parameters (e.g., iteminformation, source location information, and/or delivery locationinformation), autonomously or semi-autonomously retrieve the item(s)from a source location (e.g., a materials handling facility or a thirdparty seller), compute a route from the source location to a deliverylocation, and aerially transport the retrieved item(s) to the deliverylocation. In some implementations, the UAV will communicate with otherUAVs in the area to obtain information used in route planning. Thisinformation may be stored in a central location and/or dynamicallyshared between nearby UAVs, materials handling facilities, relaylocations, a UAV management system and/or secure delivery locations. Forexample, other UAVs may provide information regarding weather (e.g.,wind, snow, rain), landing conditions, traffic, etc. The UAV may utilizethis information to plan the route from the source location to thedelivery location and/or to modify the actual navigation of the route.In addition, in some implementations, the UAV may consider otherenvironmental factors while navigating a route. For example, if theUAV's route must cross over a road built for automobiles, the navigationof the route may be adjusted to minimize the intersection between theUAV's path and the road. For example, the UAV may alter its navigationsuch that the path of the UAV will intersect with the automobile road atan approximately perpendicular angle.

In still other implementations, the UAV may constantly monitor forhumans or other animals that may be in the path or planned path of theUAV and modify the navigation of the UAV to avoid those humans or otheranimals.

When the UAV reaches the delivery location, it will identify an area atthe delivery location where it can safely approach the ground, oranother surface, and leave the inventory item, thereby completing thedelivery. This may be done through assistance of a remote entitycontroller taking control of and/or providing control instructions tothe UAV to assist the UAV in landing at the delivery location. In otherimplementations, if the UAV has previously landed at the deliverylocation, it may use stored information about the delivery location(e.g., safe landing area, geographic coordinates of the landing area) tonavigate the landing at the delivery location. Upon completion of thedelivery, the UAV may return to a materials handling facility or anotherlocation to receive different inventory, recharge, etc.

As used herein, a materials handling facility may include, but is notlimited to, warehouses, distribution centers, cross-docking facilities,order fulfillment facilities, packaging facilities, shipping facilities,rental facilities, libraries, retail stores, wholesale stores, museums,or other facilities or combinations of facilities for performing one ormore functions of materials (inventory) handling. A delivery location,as used herein, refers to any location at which one or more inventoryitems may be delivered. For example, the delivery location may be aperson's residence, a place of business, a location within a materialshandling facility (e.g., packing station, inventory storage), anylocation where a user or inventory is located, etc. Inventory or itemsmay be any physical goods that can be transported using a UAV.

A “relay location” as used herein may include, but is not limited to, adelivery location, a materials handling facility, a cellular tower, arooftop of a building, a secure delivery location, or any other locationwhere a UAV can land, charge, retrieve inventory, replace batteries,and/or receive service.

FIG. 1 depicts a graphical user interface 100 for selecting a deliveryoption for the delivery of an item, according to an implementation. Inthis example, the user has requested to purchase an electronic devicetitled “6” Touch Screen Display” 102 sold by ABC Company. As part of thepurchase process, the user may select one or more delivery methods thatmay be used to deliver the selected item. In this example, the user hasselected “Automated Aerial Delivery” 109 with a delivery time estimate110 of 30 minutes. If the user does not desire to receive the item viaautomated aerial delivery, the user may choose another delivery optionby selecting the “Choose Another Delivery Option” 112 button. In stillanother implementation, the user may select a delivery time for theaerial delivery. For example, if the user does not desire to receive theitem, in this example, in 30 minutes, they may select another time atwhich they would like to receive the item.

In addition to selecting a delivery method, the user may choose adelivery location 114. With the implementations described herein, a usernow has the ability to choose “Bring It To Me” 114(A). With this option,the actual location of the user is determined and the UAV delivers theitem to the current location of the user. The current location of theuser may be based on, for example, a determined location of a portabledevice (e.g., mobile phone) associated with the user, the location ofthe network utilized by the user when placing the order, etc. Forexample, the user may identify their current location by allowing GlobalPositioning System (“GPS”) data to be provided by their mobile device.Alternatively, if the user is connected through a wireless network(e.g., cellular, Wi-Fi, satellite), the location of the network may bedetermined and used as the current location of the user.

In some implementations, the location of the user may be maintained andupdated until the item is delivered to the user. If the current locationof the user is determined based on the GPS data from the user's mobiledevice, the GPS data may be periodically retrieved by the UAV managementsystem (discussed below) and the delivery destination updated as the GPSdata changes. For example, the user may place an order for an item whileat home, select to have the item delivered to their current location(delivery within 30 minutes of the order) and then leave to go to theirfriend's house, which is three blocks away from their home. As theordered item is retrieved from inventory, the current location of theuser's mobile device may be determined and the delivery locationcorrespondingly updated. As such, the ordered item will be delivered tothe user while the user is at their friend's house, or any otherlocation.

In a similar manner, if the user does not desire to have the itemdelivered to their current location, another location may be selectedfrom either the list of locations 114 or select a location on thepresented map 118. The list of locations 114 may include other locationsfor which the user has received items via delivery from a UAV, otherlocations near the user that can receive UAV deliveries, or otherlocations that are configured to enable tracking of the current locationof the vehicle.

For example, the user may have previously had an item delivered using aUAV to their home, as illustrated by the home delivery location option114(B). Likewise, there may be a secure delivery location (discussedbelow) near the person's place of employment, as illustrated by the workdelivery location option 114(C). Alternatively, the user may haveidentified another location for which location information can bedetermined and used for item delivery. In this example, the user hasprovided information that can be used to determine the current locationof the user's boat. The location of the user's boat may be determinedbased on the GPS of the boat and retrieving GPS data from the boat. Instill other examples, the user can add other locations through selectionof the “Add Location” button 116 or selecting a location on the map 118.

Upon user selection of a delivery location, the estimated delivery timemay be dynamically updated to reflect the estimated amount of timeneeded for the UAV to deliver the item to the delivery location. Forexample, the user's boat may be physically farther from the sourcelocation than the user's home. As such, the delivery estimate time maychange. Upon selection of a delivery method and delivery location, theUAV management system may process the user's order for aerial deliveryto the selected delivery location.

FIG. 2 illustrates a block diagram of a top-down view of a UAV 200,according to an implementation. As illustrated, the UAV 200 includeseight propellers 202-1, 202-2, 202-3, 202-4, 202-5, 202-6, 202-7, 202-8spaced about the frame 204 of the UAV. The propellers 202 may be anyform of propeller (e.g., graphite, carbon fiber) and of a sizesufficient to lift the UAV 200 and any inventory engaged by the UAV 200so that the UAV 200 can navigate through the air to deliver the item(s)to a delivery location. While this example includes eight propellers, inother implementations, more or fewer propellers may be utilized.Likewise, in some implementations, the propellers may be positioned atdifferent locations on the UAV 200. In addition, alternative methods ofpropulsion may be utilized as “motors” in implementations describedherein. For example, fans, jets, turbojets, turbo fans, jet engines,internal combustion engines, and the like may be used (either withpropellers or other devices) to propel the UAV.

The frame 204 of the UAV 200 may likewise be of any suitable material,such as graphite, carbon fiber and/or aluminum. In this example, theframe 204 of the UAV 200 includes four rigid members 205-1, 205-2,205-3, 205-4, or beams arranged in a hash pattern with the rigid membersintersecting and joined at approximately perpendicular angles. In thisexample, rigid members 205-1 and 205-3 are arranged substantiallyparallel to one another and are approximately the same length. Rigidmembers 205-2 and 205-4 are arranged substantially parallel to oneanother, yet perpendicular to rigid members 205-1 and 205-3. Rigidmembers 205-2 and 205-4 are approximately the same length. In someembodiments, all of the rigid members 205 may be of approximately thesame length, while in other implementations, some or all of the rigidmembers may be of different lengths. Likewise, the spacing and/ororientation between the two sets of rigid members may be approximatelythe same or different.

While the implementation illustrated in FIG. 2 includes four rigidmembers 205 that are joined to form the frame 204, in otherimplementations, there may be fewer or more components to the frame 204.For example, rather than four rigid members, in other implementations,the frame 204 of the UAV 200 may be configured to include six rigidmembers. In such an example, two of the rigid members 205-2, 205-4 maybe positioned parallel to one another. Rigid members 205-1, 205-3 andtwo additional rigid members on either side of rigid members 205-1,205-3 may all be positioned parallel to one another and perpendicular torigid members 205-2, 205-4. With additional rigid members, additionalcavities with rigid members on all four sides may be formed by the frame204. As discussed further below, a cavity within the frame 204 may beconfigured to include an inventory engagement mechanism for theengagement, transport and delivery of item(s) and/or containers thatcontain item(s).

In some implementations, the UAV may be configured to reduce aerodynamicresistance. For example, an aerodynamic housing may be included on theUAV that encloses the UAV control system 210, one or more of the rigidmembers 205, the frame 204 and/or other components of the UAV 200. Thehousing may be made of any suitable material(s) such as graphite, carbonfiber, aluminum, titanium, magnesium, fiberglass, etc. Likewise, in someimplementations, the location and/or the shape of the inventory (e.g.,item or container) may be aerodynamically designed. For example, in someimplementations, the inventory engagement mechanism may be configuredsuch that when the inventory is engaged it is enclosed within the frameand/or housing of the UAV 200 so that no additional drag is createdduring transport of the inventory by the UAV 200. In otherimplementations, the inventory may be shaped to reduce drag and providea more aerodynamic design of the UAV and the inventory. For example, ifthe inventory is a container and a portion of the container extendsbelow the UAV when engaged, the exposed portion of the container mayhave a curved shape.

The propellers 202 and corresponding propeller motors are positioned atboth ends of each rigid member 205. The propeller motors may be any formof motor capable of generating enough speed with the propellers to liftthe UAV 200 and any engaged inventory thereby enabling aerial transportof the inventory. For example, the propeller motors may each be aFX-4006-13 740 kv multi rotor motor.

Extending outward from each rigid member is a support arm 206 that isconnected to a safety barrier 208. In this example, the safety barrieris positioned around and attached to the UAV 200 in such a manner thatthe motors and propellers 202 are within the perimeter of the safetybarrier 208. The safety barrier may be plastic, rubber, etc. Likewise,depending on the length of the support arms 206 and/or the length,number or positioning of the rigid members 205, the safety barrier maybe round, oval, or any other shape.

Mounted to the frame 204 is the UAV control system 210. In this example,the UAV control system 210 is mounted in the middle and on top of theframe 204. The UAV control system 210, as discussed in further detailbelow with respect to FIG. 14, controls the operation, routing,navigation, communication and the inventory engagement mechanism of theUAV 200.

Likewise, the UAV 200 includes one or more power modules 212. In thisexample, the UAV 200 includes two power modules 212 that are removablymounted to the frame 204. The power module(s) for the UAV may be in theform of battery power, solar power, gas power, super capacitor, fuelcell, alternative power generation source, or a combination thereof. Forexample, the power modules 212 may each be a 6000 mAh Lithium Polymer(lipo) battery. The power module(s) 212 are coupled to and provide powerfor the UAV control system 210 and the propeller motors.

In some implementations, one or more of the power modules may beconfigured such that it can be autonomously removed and/or replaced withanother power module while the UAV is landed. For example, when the UAVlands at a secure delivery location, relay location and/or materialshandling facility, the UAV may engage with a charging member at thelocation that will recharge the power module. In some implementations, acontainer may include a power module and when the engagement mechanismof the UAV engages with the container, the power module of the containermay provide power to the UAV. For example, when an item is beingdelivered to a secure delivery location, the power module included inthe container may be utilized to power the UAV, rather than and/or inaddition to the power modules 212 of the UAV 200. When the container isdisengaged (e.g., when placed into the secure delivery location), thepower provided by the container is removed and the UAV 200 operatesusing power from the UAV power module 212.

As mentioned above, the UAV 200 also includes an inventory engagementmechanism 214. The inventory engagement mechanism may be configured toengage and disengage items and/or containers that hold items. In thisexample, the inventory engagement mechanism 214 is positioned within acavity of the frame 204 that is formed by the intersections of the rigidmembers 205. In this example, the inventory engagement mechanism ispositioned beneath the UAV control system 210. In implementations withadditional rigid members, the UAV may include additional inventoryengagement mechanisms and/or the inventory engagement mechanism 214 maybe positioned in a different cavity within the frame 204. The inventoryengagement mechanism may be of any size sufficient to securely engageand disengage containers that contain inventory. In otherimplementations, the engagement mechanism may operate as the container,containing the inventory item(s) to be delivered. The inventoryengagement mechanism communicates with (via wired or wirelesscommunication) and is controlled by the UAV control system 210.

While the implementations of the UAV discussed herein utilize propellersto achieve and maintain flight, in other implementations, the UAV may beconfigured in other manners. For example, the UAV may include fixedwings and/or a combination of both propellers and fixed wings. Forexample, the UAV may utilize one or more propellers to enable takeoffand landing and a fixed wing configuration or a combination wing andpropeller configuration to sustain flight while the UAV is airborne.

FIGS. 3A-3G illustrate side views of various example configurations ofthe inventory engagement mechanism 214, illustrated in FIG. 2. Eachinventory engagement mechanism is configured to define a cavity intowhich inventory and/or a container containing inventory may bepositioned for the secure transport by a UAV. The cavity includes a topedge and side edges. In the examples illustrated in FIGS. 3A-3F, thecavity includes a top edge and four side edges. Two of the side edgesare not shown so that the position, arrangement and operation of theother two side edges can be illustrated. In some implementations, thecavity may include fewer or additional edges.

Turning first to FIG. 3A, the inventory 302 is positioned within theinventory engagement mechanism 314 and held in position with angledsupport arms 316A and 316B. While the examples discussed with respect toFIGS. 3A-3D refer to inventory, in other implementations, the inventoryengagement mechanisms discussed with respect to FIGS. 3A-3D operate in asimilar manner with containers.

In the example of FIG. 3A, both angled support arms are configured topivot around pivot points 318A and 318B, respectively. The pivoting ofthe angled support arms are controlled by one or more motors 320, suchas a servo motor. The motors 320 may likewise be controlled to open andclose the angled support arms by the UAV control system 210. When theangled support arms 316A and 316B are in a closed position, theinventory 302 is securely held in the inventory engagement mechanism 314and can be aerially transported by the UAV 200. When the angled supportarms are in an open position, the inventory 302 is released from theinventory engagement mechanism and exits the inventory engagementmechanism under gravitational force.

When the UAV 200 is retrieving inventory, it may position the inventoryengagement mechanism 314 over the inventory, open the angled supportarms 316A, 316B and lower itself, and thus the inventory engagementmechanism 314 down and around the inventory 302. As it reaches theinventory 302, the UAV control system 210 may instruct the motor(s) 320to begin closing the angled support arms 316A, 316B and continue toalign the inventory engagement mechanism 314 around the inventory 302 sothat as the angled support arms 316A, 316B close, the leading edge ofeach angled support arm will move underneath the inventory therebysecurely enclosing the inventory 302 in the inventory engagementmechanism 314.

Likewise, when the UAV 200 is disengaging inventory (e.g., as part ofinventory delivery), it may position itself and thus the inventoryengagement mechanism 314 over a delivery location (e.g., flat surface,ground, table, chair, balcony) and the UAV control system 210 mayinstruct the motor(s) 320 to begin opening the angled support arms 316A,316B. As the angled support arms open or move away from the inventory,gravity will extract the inventory 302 from the inventory engagementmechanism 314 and the inventory 302 will come to rest on the flatsurface. When the inventory has been disengaged, the UAV 200 mayreposition or close the angled support arms 316A, 316B and navigate awayfrom the area.

FIG. 3B illustrates another side view of an example configuration of aninventory engagement mechanism 330 that may be coupled to the UAV 200and used to engage and disengage inventory 302 to enable transport anddelivery of the inventory 302. In this example, the inventory engagementmechanism 330 includes a cavity with two angled support arms 336A, 336B.However, in comparison to FIG. 3A, only one of the angled support arms336B is configured to pivot about a point 338B. Similar to FIG. 3A, thepivot may be controlled by a motor 320, such as a servo motor. Likewise,the servo motor may be controlled by the UAV control system 210.

In the FIG. 3B example, the inventory is securely held in the inventoryengagement mechanism 330 when the angled support arm 336B is in a closedposition and will exit the inventory engagement mechanism when theangled support arm 336B is in an open position (positioned away frominventory 302).

FIG. 3C illustrates another side view of an example configuration of aninventory engagement mechanism 340 that may be coupled to the UAV 200and used to engage and disengage inventory 302 to enable transport anddelivery of the inventory 302. In this example, the inventory engagementmechanism 340 includes two angled support arms 346A, 346B. However, incomparison to FIG. 3A, rather than the entire angled support armpivoting, only the bottom protruding edges/surfaces 349A, 349B pivotabout pivot points 348A, 348B, respectively. Similar to FIG. 3A, thepivot of each bottom protruding edge 349A, 349B may be controlled by amotor 320, such as a servo motor. Likewise, the servo motor may becontrolled by the UAV control system 210.

In the FIG. 3C example, the inventory is securely held in the inventoryengagement mechanism 340 when the bottom protruding edges 349A, 349B ofeach angled support arm are in a closed position. Likewise, theinventory 302 will exit the inventory engagement mechanism 340 when oneor both of the bottom protruding edges 349A, 349B are in an openposition.

FIG. 3D illustrates another side view of an example configuration of aninventory engagement mechanism 350 that may be coupled to the UAV 200and used to engage and disengage inventory 302 to enable transport anddelivery of the inventory 302. In this example, the inventory engagementmechanism 350 includes two angled support arms 356A, 356B, each of whichhave bottom protruding edges/surfaces 359A, 359B. In comparison to FIG.3C, only one of the bottom protruding edges, in this example bottomprotruding edge 359B, is configured to pivot about a point 358B. Similarto FIG. 3A, the pivot may be controlled by a motor 320, such as a servomotor. Likewise, the servo motor may be controlled by the UAV controlsystem 210.

In the FIG. 3D example, the inventory is securely held in the inventoryengagement mechanism 350 when the bottom protruding edge 359B is in aclosed position and will exit the inventory engagement mechanism whenthe bottom protruding edge 359B is in an open position.

In FIG. 3E, the inventory 302 is enclosed in a container 361 that isremovably connected to the inventory engagement mechanism 360. Thecontainer 361 is connected with the inventory engagement mechanismthrough a series of members (e.g., pins) 362 or gears that areconfigured to engage and/or disengage the container. The positioning ofthe members 362 or gears are controlled by one or more motors 320, suchas a servo motor. Alternatively, the members 362 or gears may beelectromechanically controlled. For example, when there is no power andthus no magnetic charge, springs may cause the members 362 to move to anextended position, thereby securing the container in the inventoryengagement mechanism. Likewise, when no power is applied, the gears maybe locked into place so that the container is secured into the inventoryengagement mechanism, as discussed below. Conversely, when power isapplied, the resulting magnetic charge will cause the members to retractinto the inventory engagement mechanism, thereby releasing a previouslysecured container from the inventory engagement mechanism. Likewise,gears may be configured to freely rotate when power is applied, therebyreleasing the container from the inventory engagement mechanism.

The motors 320 may likewise be controlled to extend or retract themembers 362 or rotate the gears, by the UAV control system 210. When theinventory engagement mechanism is positioned around the container 361and the members 362 are in an extended position, the members securelyhold the container, and thus the inventory 302, in the inventoryengagement mechanism. In this example, the container has an extendedridge 364 that fits within the cavity of the inventory engagementmechanism 360. When the container is positioned within the cavity of theinventory engagement mechanism 360 and the members are in an extendedposition, the members are positioned under the ridge 364 therebysecuring the container in the inventory engagement mechanism 360. Whenthe members 362 are retracted, the container 361 is released from theinventory engagement mechanism and exits the inventory engagementmechanism 360 under gravitational force. Likewise, rather than members,gears with extended teeth may rotate within the cavity of the inventoryengagement mechanism and engage slots in the sides of the container 361.When the container is positioned within the cavity of the inventoryengagement mechanism 360, the gears may rotate and the teeth of thegears engage with slots in the side of the container 361, therebysecuring the container in the inventory engagement mechanism 360. Whenthe gears are rotated in an opposite direction, the container 361 isexpelled from the cavity of the inventory engagement mechanism 360 andreleased.

When the UAV 200 is engaging a container 361, it may position theinventory engagement mechanism 360 over the container 361 and loweritself, and thus the inventory engagement mechanism 360 down and aroundthe container 361. When the ridge 364 of the container 361 is within thecavity of the inventory engagement mechanism 360, the UAV control system210 may instruct the motor(s) 320 to begin extending the members 362such that the members become positioned beneath the extended ridge 364of the container, thereby securing the container 361 in the inventoryengagement mechanism 360. In implementations utilizing gears, the gearsmay be allowed to rotate freely as the UAV descends onto the container361. When the container is inside the inventory engagement mechanism andthe gears have rotated into the slots on the sides of the container 361,the gears may be locked into place, or prohibited from rotating in anopposite direction, thereby securing the container 361 in the cavity ofthe inventory engagement mechanism 360.

Likewise, when the UAV 200 is disengaging a container (e.g., as part ofa delivery), it may position itself and thus the inventory over asurface (e.g., ground, table, chair, balcony) and the UAV control system210 may instruct the motor(s) 320 to begin retracting the members 362 orrotating the gears in an opposite direction. When the members retract,gravity will extract the container 361 from the inventory engagementmechanism 360 such that the container 361 will come to rest on the flatsurface. Likewise, when the gears rotate in the opposite direction, thecontainer will be released from the inventory engagement mechanism andcome to rest on the surface. When the container 361 has been disengaged,the UAV 200 may navigate away from the area.

FIG. 3F illustrates another side view of an example configuration of aninventory engagement mechanism 370 that may be coupled to the UAV 200and used to engage and disengage a container 371 that holds inventory302, thereby enabling transport and delivery of the inventory 302. Inthis example, the inventory engagement mechanism 370 includes a seriesof members 372 that are configured to extend or retract, for examplethrough the use of electromagnetics as discussed above. Alternatively,or in addition thereto, the inventory engagement mechanism may utilizegears that rotate within the inventory engagement mechanism.

Similar to FIG. 3E, when the members are extended and/or the gearsrotated, they engage and secure a container 371 within the inventoryengagement mechanism 370. When the members 372 are retracted or thegears rotated in an opposite direction, the container is released fromthe inventory engagement mechanism 370. However, in comparison to thecontainer 361 illustrated in FIG. 3E, the container 371 of FIG. 3F maynot have an extended ridge 364 under which the members position.Instead, the container 371 may have one or more openings, holes or slotsinto which the members 372 and/or gears of the inventory engagementmechanism may mate with the container, thereby securing the containerinto the inventory engagement mechanism. Similar to FIG. 3E, theextending and retracting of the members and/or rotation of the gears maybe controlled by a motor 320, such as a servo motor. Likewise, the motor320 may be controlled by the UAV control system 210.

In the FIG. 3F example, the container 371 is securely held in theinventory engagement mechanism 370 when the members 372 are extended andwill exit the inventory engagement mechanism when the members 372 areretracted. Likewise, when using gears, the container 371 is securelyheld in the inventory engagement mechanism 370 when the gears arerotated and mate with the slots of the container 371 and will exit theinventory engagement mechanism when the gears are rotated in an oppositedirection and disengage with the slots of the container 371.

FIG. 3G illustrates yet another view of the inventory engagementmechanism 380 configured to engage and/or disengage a container 381 orother inventory, according to an implementation. In this example, theinventory engagement mechanism 380 may include one or more conical orother shaped extrusions 383 that extend from the inventory engagementmechanism 380 toward the container 381. Likewise, the container 381 mayinclude one or more conical or other correspondingly shaped indentations384 into which the inventory engagement mechanism 380 extrusions 383mate. As illustrated in FIG. 3G, the inventory engagement mechanism 380includes two conical shaped extrusions 383 that extend downward towardthe container 381. In other implementations, more or fewer extrusions383 may be used. Likewise, the container 381 includes correspondingconical indentations 384 into which the extrusions 383 of the inventoryengagement mechanism 380 may mate when the UAV 200 is positioned overand onto the container 381.

While the example illustrated in FIG. 3G depicts the extrusions 383extending downward and into a top of the container 381, in otherimplementations, the extrusions 383 may have other orientations. Forexample, one or more extrusions may be oriented at approximately ninetydegrees and configured to extend into a side of an indentation locatedon a side of the container 381. In one implementation, there are twoextrusions oriented to extend into opposing sides of the container 381.In such an implementation, the extrusions may be horizontally adjustablewith respect to one another to enable engagement and disengagement ofthe container. For example, the extrusions may be adjusted to an open orextended position that is wider than the container. When the UAV ispositioned over the container with the extrusions on either side of thecontainer, the extrusions may be horizontally moved to a closed orretracted position in which each extrusion mates with a respectiveindentation on the container 381, thereby engaging the container fortransport.

The shape of the extrusions and corresponding indentations provideassistance in the alignment between the UAV 200 and the container 381and the ultimate engagement of the container 381 by the inventoryengagement mechanism 383 of the UAV 200. For example, as long as thepoints 385 of the extrusions 383 pass into the openings of theindentations 384 of the container 381, the corresponding shapes willhelp align the UAV 200 as it continues to lower over the container.

Likewise, in some implementations, the extrusions 383 may include one ormore members 382 (e.g., pins) that may be used to secure the containerto the inventory engagement mechanism 380 when engaged. As discussedabove, the members 382 may be controlled by a motor (not shown), such asa servo motor. In another implementation, the members 382 may beelectromagnetically controlled. For example, springs may cause themembers 382 to extend out of the extrusions 383 when there is noelectromagnetic charge. When a charge is applied, the electromagnet maycause the members 382 to retract into the extrusions 383.

The container 381 may include one or more rings, recesses, openings, orother forms of slots 386 within the indentations 384 into which themembers 382 may extend to secure the container to the inventoryengagement mechanism 380. For example, the members 382 of the inventoryengagement mechanism 380 may be retracted while the UAV is landing onthe container 381. When the inventory engagement mechanism 380 has fullymated with the container 381, the members 382 may be released such thatthey extend into the slots 386 and secure the container 381 to theinventory engagement mechanism 380. In some implementations, the ends ofthe members 382 may be angled so that as the conical shaped extrusions383 of the inventory engagement mechanism 380 mate with the indentationsof the angle, the indentation will push the members 382 into theretracted position until they reach the slots 386 within theindentations and release, thereby securing the container 381.

While the example discussed above illustrates conical extrusions 383 andcorresponding indentations 384 that are pointed, in otherimplementations, other shapes and/or sizes of extrusions and/orindentations may be utilized. For example, the extrusions andindentations may be curved rather than pointed. Likewise, rather thanhaving the members 382 as part of the extrusions 383, in otherimplementations, the members may be included in the indentations 384 andthe corresponding slots may be included in the extrusions 383.

The examples discussed above with respect to FIGS. 3A-3G are merelyillustrative and it will be appreciated that the inventory engagementmechanism may be configured in many different forms. A feature of anyinventory engagement mechanism configuration is the ability to securelyengage and disengage inventory and/or containers so that the inventoryand/or container can be aerially transported by a UAV 200 and deliveredto a delivery location. For example, in addition to or as an alternativeto utilizing pivoting angled support arms, members and/or gears, in someimplementations, the angled support arms may be configured to move in ahorizontal direction such that the size of the cavity formed to containthe inventory 302 or container can be adjusted to account for the sizeof the inventory and/or container to be engaged, transported anddisengaged. As another example, in some implementations, the inventoryengagement mechanism may include a positioning arm and/or cable that maybe used to position, raise and/or lower inventory. In someimplementations, the positioning arm or cable may operate as theinventory engagement mechanism. In other implementations, thepositioning arm or cable may operate as part of an inventory engagementmechanism. In one implementation, a positioning cable may be includedthat removably attaches to the inventory and can be used to engage theinventory and raise the inventor up to a location of the UAV. Likewise,when the inventory is being disengaged at a delivery location, ratherthan having to land the UAV, the positioning cable may be extended sothat the inventory is lowered to the landing area. When the inventoryhas reached the landing area, the positioning cable may be detached fromthe inventory and retracted back into the UAV.

FIG. 4 depicts a block diagram of a secure delivery location 400, in oneimplementation. The secure delivery location 400 may include one or morecontrol stations 401 and one or more storage compartment modules 403,405, 407, 409. The control station 401 acts as the central control pointfor the secure delivery location 400, providing power, computingresources, user input and network access to the secure delivery location400. For example, control station 401 may include an internal computingsystem (not shown), or other computing system, that is capable ofmaintaining state information for each storage compartment at the securedelivery location 400 and providing other computing functions. Forexample, the internal computing system may include a command componentthat maintains information as to which storage compartments of thesecure delivery location 400 are empty, which storage compartmentsinclude inventory items and/or containers that contain inventory items,the access code(s) or other identifier(s) necessary to open each of thestorage compartments and any other information necessary to maintain thesecure delivery location. The command component may also issue commandsor instructions to the storage compartment modules to lock/unlockstorage compartments, active and/or deactivate sensors, and the like.

The secure delivery location 400 may be configured to obtain and/orprovide information to a remote computing resource, such as the UAVmanagement system (FIG. 5), UAVs, materials handling facilities, relaylocations, or may be configured to operate primarily as a stand-aloneunit, with limited external communication.

In communicating with UAVs, the control station 401 may be configured toidentify when a UAV is arriving, determine a storage compartment module403, 405, 407, 409 into which the UAV is to place a container 480, openthe storage compartment module to allow placement of the container 480by a UAV and/or take control of the UAV to assist in landing the UAV atthe secure delivery location 400. For example, as a UAV approaches thesecure delivery location 400, the control station 401 may identify theUAV and determine that the UAV is to disengage a container 480 into thestorage compartment module 403. The top doors 403(A) and 403(B) of thestorage compartment module 403 may be opened by the control system 401and one or more cameras 406, and/or other input components, activated tomonitor the position of the UAV 200 (not shown). The cameras 406 may bepositioned inside the storage compartment modules and only visibleexternally when the top doors are opened, may be positioned on anotherexterior surface of the secure delivery location 400 and/or may bepositioned remote from the secure delivery location 400 and incommunication (e.g., wired and/or wireless) with the control station401.

As the UAV approaches, the control station 401 may operate as a remoteentity controller and request control of the UAV so that it can controlthe landing of the UAV and/or disengagement of the container 480 intothe opening of the storage compartment module 403. As discussed belowwith respect to FIG. 13, upon taking control of the UAV, the controlstation 401 may monitor the position of the UAV by processing images ofthe UAV captured by the one or more cameras 406 and provide navigationinstructions to the UAV that will cause the UAV to descend over theopening in the storage compartment module 403 and insert the container480 into the opening of the storage compartment module 403. In someimplementations, a series of instructions may be provided to the UAV bythe remote entity controller to enable positioning of the UAV over thestorage compartment module 403. For example, the remote entitycontroller may capture one or more images of the UAV, determine andprovide instructions to the UAV and the UAV may execute theinstructions. During and after execution of the instructions, the remoteentity controller may continue to monitor the UAV and provide additionalinstructions to the UAV. This process may continue until the UAV haslanded or reached a determined height above the landing area.

In some implementations, the sides of the container 480 include slots481 that are configured to mate with the gears of the inventoryengagement mechanism of the UAV (discussed above) as well as mate withgears 408 within the storage compartment module 403. As the container islowered by the UAV into the opening of the storage compartment module403, the gears 408 within the storage compartment module 403 may rotatesuch that the teeth of the gears mate with the slots 481 of thecontainer 480, thereby securing the container 480 in the storagecompartment module 403. Once the container 480 is secured by the storagecompartment module 403, the control station 401 may instruct the UAV todisengage the container 480.

In other implementations, rather than having the UAV lower the containerinto the storage compartment module 403, in some implementations, whenthe top doors of the storage compartment module 403 open, a shelf (notshown) or other support platform may be extended out of and above theopening of the storage compartment module 403. In such animplementation, the UAV may place the container 480 onto the shelf anddisengage from the container 480. Once the UAV has disengaged from thecontainer 480, the shelf and container 480 may be lowered back into thestorage compartment module 403 and secured.

In some implementations, the gears 408 of the storage compartment module403 may be configured to provide electrical connectivity to thecontainer 481 and/or through the container to the UAV. As noted above,the container 480 may include a power module 482 and the gears 408 maybe configured so that when the container 480 is engaged, the connectionbetween the gears 408 and the container 480 can be used to provide powerto and recharge the power module 482. Likewise, gears may also beconfigured to provide electrical connection to the UAV to recharge thepower module 212 of the UAV 200.

Once the UAV 200 has disengaged the container 480 and separated, thecontrol system 401 may coordinate the placement of the container withinthe secure delivery location 400, provide a notification to theinventory management system that the item has been delivered and/ornotify the customer that the item has been delivered to the securedelivery location 400 and is available for retrieval. For example, thegears 408 may be used to move the container 480 within the securedelivery location 400 and position the container 480 in one of thestorage compartments 433. The container may be configured such that itis the same size as a storage compartment 433 and such that the frontside 410 of the container 480 will open when the user is provided accessto the storage compartment 433.

The control station 401 may also include a user interface 411. The userinterface 411 is configured to receive and provide information to one ormore users of the secure delivery location 400 and may include, but isnot limited to, a display 413, such as a touch-screen display, a scanner415, a keypad 417, a biometric scanner 419, an audio transducer 421, oneor more speakers 423, one or more image capture devices 425, such as avideo camera, and any other types of input or output devices that maysupport interaction between the secure delivery location 400 and one ormore users. For example, the user interface 411 may also include acredit card reader, the ability to accept money (such as cash or coins)and/or the ability to vend items (e.g., labels, envelopes, shippingpackages) using a vending slot 426. Providing the ability for the securedelivery location 400 to accept credit cards and/or money enables thedelivery of items to a storage compartment at the secure deliverylocation 400 for which the items are paid for at the time of pickup(e.g., cash on delivery). Likewise, enabling vending of items, such aslabels or envelopes, supports the ability for users to utilize a securedelivery location to ship or deliver goods. In some implementations,items that are frequently purchased (often referred to as high velocityitems) may be delivered to and stored in the secure delivery locationprior to anyone ordering the item. When the item is ordered, it may bemade available to the user for retrieval from the secure deliverylocation and/or the secure delivery location 400 may act as a sourcelocation, providing a container that includes the ordered item to a UAVthat retrieves the container from the secure delivery location andprovides it to another user selected delivery location.

The control station 401 may also include a connector componentconfigured to provide wired and/or wireless network connectivity withthe other storage compartment modules 403, 405, 407, 409, as well as toremote computing devices (FIG. 5), materials handling facilities and/orUAVs. Wireless connectivity may be implemented using a wireless antenna431, which may provide both receive and transmit functionality. Powerand/or network communication with remote computing devices may beobtained from a main access point 432. In addition, in someimplementations, the control station 401 may include one or more storagecompartments 435, 437, 439. In comparison to the storage compartments435, 437, 439 of the storage compartment modules, these storagecompartments may store UAVs and/or parts, such as batteries, propellers,jets, etc., for use in servicing a UAV. Likewise, in someimplementations, other storage compartment modules, such as storagecompartment module 409 may not be configured to autonomously receivecontainers from UAVs. Instead, these storage compartment modules mayoperate in a more traditional manner providing storage for items,inventory, parts, UAVs, etc. For example, storage compartment 467 mayinclude a number of shelves, each of which are configured to store a UAVthat can be deployed by the control station 401 and/or by the UAVmanagement system 526 (FIG. 5). In some implementations, the storagecompartment 467 may be configured to provide a charge to the UAVs sothat when deployed the UAVs will be fully powered for flight. Whendeploying a stored UAV, the control station 401 may provide instructionsto open the door of the storage compartment 467 so that UAVs candisengage and fly out of the storage compartment. In such animplementation, access to the storage compartment and/or the door of thestorage compartment may be oriented away from any area in which a humanmay interact with the secure delivery location 400.

A stored UAV, when deployed, may be used to expand the capacity of theUAV network and used to retrieve an item from a source location anddeliver it to a destination location. Alternatively, a UAV may bedeployed to replace another UAV that needs to be removed from service(e.g., to recharge and/or for repairs). In still other implementations,a UAV may only be temporarily deployed to assist in reconfiguring theplacement of containers within a storage compartment module 403, 405,407, 409 of the secure delivery location 400. For example, if thecontainers need to be repositioned such that empty containers can beretrieved and returned to the materials handling facility, a UAV 200 maybe deployed to retrieve containers from the opening of the top of thestorage compartment module, and reposition the containers within thesecure delivery location 400.

The control station 401 may also include one or more connectorcomponents to which a storage compartment module, such as storagecompartment module 405 or storage compartment module 407 may connectwith the control station 401. For example, a connector component mayprovide power to storage compartment module 405 and another connectorcomponent may provide communication with storage compartment module 405.Likewise, the storage compartment modules may also include one or moreconnector components to provide power and connectivity to additionalstorage compartment modules.

Each storage compartment module, such as storage compartment modules403, 405, 407, 409, may be configured so the secure delivery location400 is modular, such that one or more storage compartment modules can beeasily removed or added to the control station 401 of the securedelivery location 400. The ability to add or remove storage compartmentmodules at a secure delivery location 400 supports the ability to easilyand quickly expand or remove capacity so that the demand for that securedelivery location can be satisfied. For example, during the holidayseason, additional storage compartment modules may need to be added tothe secure delivery location 400 to support the increased demand ofitems ordered by users. As storage compartment modules 403, 405, 407,409 are added or removed from a secure delivery location 400, thecontrol station 401 informs the UAV management system 526 of the addedor removed capacity.

Each storage compartment module 403, 405, 407, 409 includes one or morestorage compartments, one or more receptor components for connectingwith connector components of a control station 401 (or another storagecompartment module) and one or more connector components for allowingother storage compartment modules to connect thereto, thereby providingpower and/or connectivity with the control station 401. The storagecompartments of each storage compartment module may be of varying sizesand number. As shown, different storage compartment modules may beconfigured to receive and provide access to different sizes ofcontainers. For example, storage compartment module 403 may beconfigured such that the storage compartments 433 are large enough toreceive containers the size of container 480. In comparison, the storagecompartment module 407 may have smaller storage compartments 449 thatare configured to receive smaller containers. As such, storagecompartment modules with different storage compartment sizes can beadded to a secure delivery location 400 to optimize the storagecompartment configuration to match that of the sizes of containerstypically scheduled for aerial delivery to the secure delivery location.

In addition to including storage compartments, power and connectivitypoints, the storage compartment modules 403, 405, 407, 409 may alsoinclude one or more wireless antennas and/or one or more generalcomputing systems, or a simpler computing system such as a printedcircuit board, RFID tag, or anything else that may be detectable by thecontrol station 401 and used to identify the storage compartment module.The computing component(s) of each storage compartment module mayinclude a unique identifier of the storage compartment module andconfiguration information of the storage compartment module, whichincludes dimension information and location information of each storagecompartment of the storage compartment module. The computing componentmay also include a storage compartment management component configuredto control movement of containers between the storage compartmentsand/or to control the actuators that enable locking and unlocking of thestorage compartment doors of the storage compartment module 403, 405,407, 409 in response to receiving commands or instructions from acommand component of the control station 401.

A storage compartment module, such as storage compartment module 407,when added to a control station 401 and power is applied, providesinformation to the control station 401 identifying the storagecompartment module 407, the number, location, and dimensions of eachstorage compartment of the storage compartment module and any otherconfiguration or information necessary to enable the control station 401to control the storage compartment module 407. It will be appreciatedthat any number, size and configuration of storage compartments of astorage compartment module may be utilized with the variousimplementations described herein.

In an alternative implementation, rather than providing all of theinformation from the storage compartment module to the control station401, the storage compartment module 407 may only provide limitedinformation, such as an identifier, to the control station 401. Thecontrol station 401, upon receiving the limited information from anadded storage compartment module 407, may make a request to a remotecomputing system, such as the UAV management system, and obtaininformation about the configuration, number and sizes of the storagecompartments of the added storage compartment module 407.

The control station 401, upon receiving identifying information of anadded storage compartment module 407, may allocate the added capacity tothe secure delivery location 400. In various implementations, the addedstorage compartment module may act as a slave component for the controlstation, receiving instructions (e.g., open storage compartment, opentop doors of storage compartment module, move containers between storagecompartments, close storage compartment, activate image capture device,monitor motion sensor) from the command component of the control station401 and providing responses (e.g., closed-door, closed, open-door,object/movement detected, container moved) to the control station 401via the storage compartment management component.

Each storage compartment of a storage compartment module 403, 405, 407,409 or control station 401 includes upper, bottom, side and rearsurfaces and at least one door configured to form a cavity in whichitems and/or containers may be positioned. For example, the uppersurface and bottom surface of the storage compartment may be open sothat a container may pass through the storage compartment. Likewise,gears 408 may be on the side surfaces to control the movement ofcontainers 480 into and out of the storage compartment, secure thecontainer in the storage compartment and/or charge a power module 482included in the container 480. In some implementations, the storagecompartments and/or the storage compartment module may be configuredsuch that containers can be moved horizontally (side-to-side orfront-to-back) so that other containers can move vertically within thestorage compartment module. For example, in some implementations,containers may be received on the left side of a storage compartmentmodule, be positioned within a storage compartment of the storagecompartment module until the contained item is removed and then movedhorizontally to the right side (or back) of the storage compartmentmodule until the empty container is retrieved by a UAV, or anotherentity, and removed from the secure delivery location.

In addition, each storage compartment may include various security orother components. For example, looking at the expanded view of storagecompartment 457, disposed within the cavity the storage compartment mayinclude a locking mechanism 469, which may be controlled remotely by thecommand component of the control station 401 via the storage compartmentmanagement component. The locking component may be configured to securethe door 475 in a closed position. Likewise, the locking component maybe configured to engage with the side 410 of the container 481 such thatwhen the door 475 of the storage compartment 457 opens the side 410 ofthe container 480 also opens. The locking mechanism 469 may becontrolled by the control station 401, either through wired or wirelesscommunication with the storage compartment management component, toeffect locking and unlocking of the door 475 of the storage compartment457 and/or the container 480. For example, when a user interacts withthe control station 401 via the display 413 and provides an access codeor other identifier, the control station 401 may identify a specificstorage compartment associated with the access code or other identifierand the command component may wirelessly send instructions to thestorage compartment management component of the storage compartmentmodule 407 to unlock a storage compartment 457. The instructions mayinclude a command (e.g., unlock), an address or identifier of thespecific storage compartment and any other information necessary forcommunication between the control station 401 and the storagecompartment module 407. In response to receiving the instructions fromthe command component, the storage compartment management component ofthe storage compartment module 407 may activate a locking mechanism thatmoves the members of the locking mechanism 469 on the door 475 of theidentified storage compartment 457 such that the members retract,thereby disengaging the lock of the storage compartment 457 allowing thedoor 475 to open. In some implementations, the storage compartment 457may also include an interior latch and spring mechanism (not shown) suchthat when the locking mechanism 469 of the storage compartment 457 isdisengaged the latch engages the side 410 of the container and thespring mechanism propels the door 475 of the storage compartment 457 andthe side 410 of the container outward, thereby identifying to a userthat the door 475 is unlocked and the storage compartment 457 isaccessible.

While the locking mechanism described above utilizes retractable membersand a latch, any mechanical, magnetic, electrical or other form oflocking mechanism may be utilized with the various implementationsdescribed herein. In addition, the storage compartment 457 may alsoinclude magnets to help retrieve a door when it is not all the wayclosed. Also, the locking mechanism of different storage compartmentsand different storage compartment modules may be the same or different.

As containers are emptied by users retrieving delivered items, thecontrol system 401 may reposition the containers so that containers withitems are at a level easily accessible by users, while empty containersare higher in the storage compartment to facilitate retrieval and returnof empty containers to the materials handling facility. For example,empty containers may be moved horizontally (side-to-side and/orfront-to-back) within the storage compartment module so that othercontainers can be positioned within the storage compartment module.

Some storage compartments, such as any of the storage compartmentsand/or containers 480, may be refrigerated. In various implementations,such refrigerated storage compartments and/or containers may includetheir own cooling mechanisms or may rely on those of neighboringrefrigerated storage compartments to which they are environmentallycoupled, or alternatively each of the modules 401, 403, 405, 407, 409 orthe entire secure delivery location 400 may have a centralized coolingsystem. The temperature of previously non-refrigerated storagecompartments may be adjusted to become refrigerated storage compartmentsand vice-versa. The temperature in each of the refrigerated storagecompartments and/or containers may be separately adjustable, such thatitems inside each of the refrigerated storage compartments and/orcontainers may be cooled to a desired temperature. For example, when acontainer positioned at one of the storage compartments is to berefrigerated, its temperature may be controlled by the control system401. For example, the control system may provide cooling around thecontainer thereby cooling the interior of the container. Alternatively,an access point may be available in the container to allow airflow intoand/or out of the container to assist in cooling the container. In stillanother example, the container itself may have cooling capabilities anddraw power from the container's power module to operate the cooling ofthe container. As noted above, the power module of the container may becharged by the secure storage location while the container is within thesecure storage location 400.

In another example, the secure delivery location 400 may also include astorage compartment module configured as a drop-box (not shown). Ratherthan utilizing specific storage compartments of the secure deliverylocation 400 to store returned items and/or items for delivery, astorage compartment module configured as a drop-box may be utilized tosecurely store such items. For example, a drop-box may be configuredwith a pivoting door, lid or tray that allows items to be placed in thedrop-box but not retrieved without having additional access to thedrop-box. For example, a pivoting lid may be configured on the storagecompartment so that a UAV can position itself over the storagecompartment and disengage inventory and/or a container. The disengagedinventory and/or container will pass through the pivoting lid and intothe drop-box. When a user arrives at the storage compartment, they mayprovide a personal identification number (PIN) or other identifier togain access to the drop-box and retrieve the item.

The storage compartment modules 403, 405, 407, 409 as well as thecontrol station 401 may also include self-leveling feet 479 that may beused to level the storage compartment modules 403, 405, 407, 409 and/orcontrol station 401 when located on un-level surfaces. In addition, theself-leveling feet 479 may also be adjusted so that a storagecompartment module, such as storage compartment module 405, 407, can bepositioned so it is flush and aligned with a control station 401 oranother storage compartment module. As an alternative to self-levelingfeet 479, any other type of support mechanism may be utilized withvarious implementations described herein for supporting the controlstation 401 or any storage compartment module 403, 405, 407, 409. Also,the control station 401 and one or more of the storage compartmentmodules 403, 405, 407, 409 may utilize different types of supportmechanisms. For example, the control station 401 may utilizeself-leveling feet while the storage compartment modules 403, 405, 407,409 may utilize rolling casters or wheels. The casters/wheels mayfurther enable the ease with which storage compartment modules may beadded or removed from a control station 401, thereby allowing the easyaddition/removal of capacity at the secure delivery location 400.

In some implementations, the secure delivery location may be of a sizeto prevent interference between UAVs and humans. For example, a securedelivery location may be built so that it is taller than the averagehuman or taller than the reach of an average human. In oneimplementation, the secure delivery location may be ten feet tall. Insuch an implementation, the storage compartments that are out of thereach of most humans may be utilized to store empty containers, partsfor UAVs (e.g., batteries, propellers), computing components, UAVs,etc., and/or for use in repositioning containers within the securedelivery location.

As another example, portions of the secure delivery location that mayreceive or provide containers to UAVs or otherwise interact with UAVsmay be separated from areas where humans may interact with the securedelivery location 400. For example, the secure delivery location 400 maybe inside a facility or have a covering that extends out from a top ofthe secure delivery location. If the secure delivery location is insidea facility, the top of the secure delivery location 400 may extendthrough a roof of the facility or otherwise have external access thatseparates the top of the secure delivery location from humans. Likewise,a covering extending from the secure delivery location separates areasof the secure delivery location accessed by humans from areas in which aUAV may operate.

While the illustrated examples describe a UAV providing a container intoa top of a secure delivery location 400, in other implementations, thecontainer may be provided into a rear, side or front of the securedelivery location 400.

While the example discussed above, describes a secure delivery locationthat is capable of receiving multiple containers, in someimplementations, the secure delivery location may be a simplifiedversion that is configured for personal and/or family use (referred toherein as a personal secure delivery location). For example, a personalsecure delivery location may be positioned at a person's home andinclude components similar to those of the secure delivery locationdiscussed above. However, rather than having multiple storagecompartments, it may be configured to only have an opening top and/or areduced number of storage compartments. Like the secure deliverylocation discussed above, a personal secure delivery location mayinclude, among other things, an opening top (to facilitate containerdelivery) that can be opened by an included computing system, a camerato monitor an arriving UAV, and an access panel to control user accessto the personal secure delivery location. In such an implementation,when a UAV arrives at the personal secure delivery location, thecomputing system may cause the top door of the personal secure deliverylocation to open and guide the landing of the UAV and/or thedisengagement of the container or item into the secure deliverylocation. The container and/or item may not be engaged by the personalsecure delivery location (e.g., with gears) but may instead just come torest inside the cavity of the personal secure delivery location. Whendisengagement of the item(s) or the container has been completed, thepersonal secure delivery location may cause the top door to close,thereby securing the item, and inform the user and/or the UAV managementsystem that the item has been delivered. In some implementations, thepersonal secure delivery location may also provide charging to the UAV.

FIG. 5 depicts a block diagram of a UAV environment 500 that includesUAVs 200, secure delivery locations 400, relay locations 502, materialshandling facilities 504 and remote computing resources 510, according toan implementation. Each of the UAVs 200, secure delivery locations 400,relay locations 502, materials handling facilities 504 and/or remotecomputing resources 510 may be configured to communicate with oneanother. For example, the UAVs 200 may be configured to form a wirelessmesh network that utilizes Wi-Fi or another wireless means ofcommunication, each UAV communicating with other UAVs within wirelessrange. In other implementations, the UAVs 200, UAV management system526, materials handling facilities 504, relay locations 502 and/or thesecure delivery locations 400 may utilize existing wireless networks(e.g., cellular, Wi-Fi, satellite) to facilitate communication.Likewise, the remote computing resources 510, materials handlingfacilities 504, secure delivery locations 400 and/or relay locations 502may also be included in the wireless mesh network. In someimplementations, one or more of the remote computing resources 510,materials handling facilities 504, secure delivery locations 400 and/orrelay locations 502 may also communicate with each other via anothernetwork (wired and/or wireless), such as the Internet.

The remote computing resources 510 may form a portion of anetwork-accessible computing platform implemented as a computinginfrastructure of processors, storage, software, data access, and othercomponents that is maintained and accessible via a network, such as themesh network and/or another wireless or wired network (e.g., theInternet). As illustrated, the remote computing resources 510 mayinclude one or more servers, such as servers 520(1), 520(2), . . . ,520(N). These servers 520(1)-(N) may be arranged in any number of ways,such as server farms, stacks, and the like that are commonly used indata centers. Furthermore, the servers 520(1)-(N) may include one ormore processors 522 and memory 524 which may store a UAV managementsystem 526.

The UAV management system 526 may be configured, for example, tocommunicate with the secure delivery locations 400, UAVs 200, materialshandling facilities 504, and/or relay locations 502. As an example, anaccess code may be synchronized between a control station 401 and theremote computing resources 510 so that the access code can be providedto a customer once the item has been delivered and used by the customerto retrieve the item.

When a message is sent to or from a UAV, the message may include anidentifier for the UAV and each UAV may act as a node within thenetwork, forwarding the message until it is received by the intendedUAV. For example, the UAV management system 526 may send a message toUAV 200-6 by transmitting the message and the identifier of the intendedreceiving UAV to one or more of UAVs 200-1, 200-2, 200-3 that are inwireless communication with the UAV management system 526. Eachreceiving UAV will process the identifier to determine if it is theintended recipient and then forward the message to one or more otherUAVs that are in communication with the UAV. For example, UAV 200-2 mayforward the message and the identification of the intended receiving UAVto UAV 200-1, 200-3 and 200-5. In such an example, because 200-3 hasalready received and forwarded the message, it may discard the messagewithout forwarding it again, thereby reducing load on the mesh network500. The other UAVs, upon receiving the message, may determine that theyare not the intended recipients and forward it on to other nodes. Thisprocess may continue until the message reaches the intended recipient.

In some implementations, if a UAV loses communication with other UAVsvia the wireless mesh network, it may activate another wirelesscommunication path to regain connection. For example, if a UAV cannotcommunicate with any other UAVs via the mesh network 500, it mayactivate a cellular and/or satellite communication path to obtaincommunication information from the UAV management system 526, materialshandling facility 504, relay location 502 and/or a secure deliverylocation 400. If the UAV still cannot regain communication and/or if itdoes not include an alternative communication component, it mayautomatically and autonomously navigate toward a designated location(e.g., a nearby materials handling facility 504, relay location 502and/or secure delivery location 400).

The wireless mesh network 500 may be used to provide communicationbetween UAVs (e.g., to share weather information, location information,routing information, landing areas), UAV management system 526,materials handling facilities 504, secure delivery locations 400 and/orrelay locations 502. Likewise, in some implementations, the wirelessmesh network may be used to deliver content to other computingresources, such as personal computers, electronic book reading devices,audio players, mobile telephones, tablets, desktops, laptops, etc. Forexample, the mesh network may be used to deliver electronic book contentto electronic book reading devices of customers. For example, one ormore secure delivery locations 400, relay locations 502, materialshandling facilities 504, the UAV management system 526, and/or UAVs mayinclude a storage medium that contains digital content that may beprovided to other computing devices.

FIG. 6 depicts a block diagram of a UAV 200 landing at an attendeddelivery location, according to an implementation. In thisimplementation, the remote entity controller is a portable device 600 ofthe user. For example, the remote entity controller may be anapplication executing on a user's portable device, such as a laptop,mobile phone, tablet, etc. In general, the portable device 600 may beany portable device 600 capable of executing a software program,communicating wirelessly with the UAV 200 (e.g., Wi-Fi, Bluetooth, NearField Communication (NFC), cellular) and, in some embodiments, capableof capturing one or more images and/or video of the UAV using an imagecapture device 602, such as a camera.

In such an implementation, the user may be asked to position theirportable device 600 with the camera facing upward on a surface wherethey would like to have the item delivered. For example, the user mayplace their phone on a table outside their house with the camera facingupward. As the UAV 200 approaches the delivery location, for exampleusing GPS data, the remote entity controller sends a request to the UAV200 to take control of the UAV for landing and disengagement of theinventory and/or container. The UAV 200 may provide control to theremote entity controller and receive commands from the remote entitycontroller. Once control has been established by the remote entitycontroller operating on the user's portable device 600, the inputcomponent 602 may capture one or more images of the UAV 200, determineposition, altitude, speed, etc. of the UAV and provide instructions thatare executed by the UAV to facilitate a safe landing. In someimplementations, a series of instructions may be provided to the UAV bythe remote entity controller to enable landing of the UAV. For example,the remote entity controller may capture one or more images of the UAV,determine and provide instructions to the UAV and the UAV may executethe instructions. During and after execution of the instructions, theremote entity controller may continue to monitor the UAV and provideadditional instructions to the UAV. This process may continue until theUAV has landed or reached a determined height above the landing area.

In addition to the images, the UAV may provide information to the remoteentity controller. For example, the UAV 200 may provide location,altitude, speed, weight, etc. to the remote entity controller. Likewise,the UAV 200 may monitor the surrounding environment to confirm that thelanding area is safe and free of any humans or other animals. In someimplementations, the remote entity controller may guide the UAV downdirectly above the device 600 and the inventory may be disengaged andcome to rest on the device 600. In other implementations, the remoteentity controller may navigate the UAV 200 to a safe landing area nearthe device 600 so that when the inventory and/or container aredisengaged they come to rest near, but not on the device 600.

When the UAV 200 lands, or reaches a determined height over the landingarea, the remote entity controller provides instructions to the UAV todisengage the inventory and/or the container, or to perform otheractions. In alternative implementations, the remote entity controller,after landing the UAV 200 may return control to the UAV 200 and the UAV200 may determine the action(s) to be performed.

While the above example describes an attended landing using a portablecomputing device 600 of the user, in other implementations, otherdevices may be used to assist and/or control the landing of the UAV 200.For example, a camera (e.g., web-cam) positioned inside the user's houseor another location that is capable of obtaining images and/or video ofthe UAV 200 may be utilized.

In still other implementations, unattended landings may be performed bythe UAV without assistance from a remote entity controller. For example,if the UAV has previously landed at a delivery location, the coordinatesof the landing area may be utilized and the UAV may land at the samecoordinates. In such an implementation one or more sensors of the UAVmay be utilized to assist in the landing. For example, a time of flightsensor, radar, sonar, camera, infrared sensor, or other input componentthat is capable of determining the landing area configuration may beused by the UAV to guide the UAV to a safe landing.

In still another implementation, the landing and/or takeoff (or otheroperations) of the UAV may be manually performed or otherwise assistedby a user at the location and/or by a user at a remote location. Forexample, one or more images or other information obtained by the UAVand/or a remote entity controller (e.g., customer's phone) may beprovided to a remote location where a user views the images and controlsthe landing of the UAV. In one implementation, the images and/or otherinformation are provided over a wireless network, such as the wirelessnetwork discussed above with respect to FIG. 5, using a cellularnetwork, etc., to a human operator that takes control of the UAV toperform the landing and/or takeoff of the UAV (or other operations).Control instructions may be provided from the human operator over thewireless network to control the UAV.

In still another example, the landing and/or takeoff (or otheroperations) may be semi-autonomous. For example, as a UAV prepares toland and/or takeoff, one or more images of the area surrounding the UAVor other information may be provided by the UAV to a user at a remotelocation and the user may provide an authorization before the UAV takesoff or lands.

FIG. 7 is a flow diagram illustrating an example process for presentingan unmanned aerial vehicle delivery option for an item, according to animplementation. This process, and each process described herein, may beimplemented by the architectures described herein or by otherarchitectures. The process is illustrated as a collection of blocks in alogical flow. Some of the blocks represent operations that can beimplemented in hardware, software, or a combination thereof. In thecontext of software, the blocks represent computer-executableinstructions stored on one or more computer readable media that, whenexecuted by one or more processors, perform the recited operations.Generally, computer-executable instructions include routines, programs,objects, components, data structures, and the like that performparticular functions or implement particular abstract data types.

The computer readable media may include non-transitory computer readablestorage media, which may include hard drives, floppy diskettes, opticaldisks, CD-ROMs, DVDs, read-only memories (ROMs), random access memories(RAMs), EPROMs, EEPROMs, flash memory, magnetic or optical cards,solid-state memory devices, or other types of storage media suitable forstoring electronic instructions. In addition, in some implementationsthe computer readable media may include a transitory computer readablesignal (in compressed or uncompressed form). Examples of computerreadable signals, whether modulated using a carrier or not, include, butare not limited to, signals that a computer system hosting or running acomputer program can be configured to access, including signalsdownloaded through the Internet or other networks. Finally, the order inwhich the operations are described is not intended to be construed as alimitation, and any number of the described operations can be combinedin any order and/or in parallel to implement the process.

The example process 700 begins by receiving a request to view and/ororder an item for delivery, as in 702. For example, as discussed abovewith respect to FIG. 1, a user may request to view and/or order an item,such as an electronic device. In response to receiving a request to viewand/or order an item for delivery, a delivery location is determined, asin 704. In some implementations, a delivery location may be a defineddelivery location associated with a user account of a user that isaccessing an e-commerce shopping site. In other implementations, thedelivery location may be determined based on the current location of theuser and/or a device associated with the user that requested to viewand/or order the item. For example, if the user has identified theirportable device as a device that can be used to determine the userscurrent location, the position (e.g., GPS position) of the portabledevice may be determined by requesting that the portable device provideposition information. In another implementation, the location of thedevice utilized by the user to request to view and/or order the item maybe determined. For example, if the user requested to view and/or orderthe item using a device that includes a GPS receiver, the GPScoordinates of the device may be included in the request to view and/ororder the item. Likewise, if the device is connected to a wirelessnetwork (e.g., Wi-Fi, cellular, satellite) the location of the devicemay be determined and used as the default location. For example, manyWi-Fi networks have been mapped and associated with specific locations.The Wi-Fi network may be identified and the corresponding locationdetermined. In still another example, the user may identify theirlocation.

Based on the determined delivery location, a delivery time estimate forautomated aerial delivery is determined, as in 706. An example processfor determining a delivery time estimate for automated aerial deliveryis discussed below with respect to FIG. 8.

Upon determining the delivery time estimate, the example process 700provides one or more delivery options to the user for selection, as in708. For example, the user may be presented with an automated aerialdelivery option, which could be as fast as 30 minutes or less, overnightdelivery, ground delivery, etc. In response to providing one or moredelivery options, the user may select a delivery option and order theitem for delivery to a designated delivery location, as in 710.

FIG. 8 is a flow diagram illustrating an example aerial deliveryplanning process 800, according to an implementation. The exampleprocess 800 begins receiving a source location, a delivery location anditem information. As discussed above, the source location may be thelocation of the item or items that are to be retrieved by a UAV fordelivery to a delivery location. For example, the source location may bea materials handling facility, a secure delivery location, a third partyseller, or any other location from which an item may be retrieved fordelivery. Likewise, the delivery location may be any location specifiedby a user for delivery of an item(s). Item information may include,among other things, an identification of the ordered item(s), the size,shape and/or weight of the ordered item(s), whether the item(s) isfragile, hazardous, etc.

Based on the provided information, a UAV is selected that will provideaerial delivery of the item(s), as in 804. Many factors may beconsidered in selecting a UAV for item delivery. For example, the size,shape and/or weight of the item(s) may be considered in determining thesize and/or type of UAV that will be used to deliver the item(s) to thedelivery location. Heavier items may require a larger UAV and/or onewith a larger number of propellers and/or power module(s). Likewise,larger items may require a larger UAV to complete aerial item delivery.In addition to the size, shape and/or weight of the item, the availableUAVs in the area where the item is to be retrieved and/or delivered maybe considered. In other implementations, addition factors, such asoptimizing for the use and/or distribution of the UAVs may be consideredas a factor in selecting an available UAV. Once a UAV in the area wherethe item is to be retrieved and or delivered has been selected, a powerrequirement estimate for the selected UAV may be determined, as in 806.The power requirement estimate may be based on, for example, the weightof the UAV, the power consumption of the UAV, the weight of the item(s)to be delivered, the distance from the UAV to the source location, thedistance from the source location to the destination location, theweather (higher winds may require additional power requirements), etc.

Based on the power requirements needed for the UAV to complete aerialitem delivery, a power module is selected for the UAV, as in 807. Forexample, different power modules may be utilized depending on thedetermined power requirements needed. For example, smaller, lighterweight power modules that provide less power and/or power modules thatare not fully charged may be utilized for delivers with lower powerrequirements (e.g., shorter deliveries and/or delivers of lighteritems). In comparison, larger and/or multiple power modules may beutilized for deliveries with higher power requirements (e.g., longerdeliveries and/or deliveries of heavier items).

In addition to selecting a power module(s), a determination may be madeas to whether one or more relay locations are to be included in theroute from the source location to the delivery location, as in 808. Arelay location may be included if it is determined that the powerrequirement estimate exceeds the power available to the UAV. Forexample, a relay location may be added as a way point in the route sothat the UAV can land at the relay location and either recharge orobtain different and/or additional power modules.

If it is determined that a relay location is to be included in theroute, a relay location that is near or along the route from the sourcelocation to the delivery location is determined, as in 810. In additionto determining the relay location, a determination is made as to whethera power module that will provide sufficient power to the UAV isavailable at the relay location for use by the UAV, as in 812. Forexample, a relay location may include additional power modules that canbe used to replace extinguished power modules of the UAV. If it isdetermined that a power module is available at the relay location, thepower module is reserved for the UAV, as in 814. However, if it isdetermined that a power module is not available at the relay location, arecharge time may be added to the delivery time estimate, as in 816. Forexample, a time required to recharge the power module of the UAV to asufficient level to allow delivery of the item(s) to the deliverylocation and transport of the UAV to another location may be determinedand included in the delivery time estimate. In an alternativeimplementation, a different relay location may be selected.

After including a recharge time in the delivery time estimate, or if itis determined that the relay location is not to be included in the routebetween the source location and the delivery location, the delivery timeestimate is determined and provided, as in 818. For example, thedelivery time estimate may be provided to the user as part of theexample process 700, discussed above with respect to FIG. 7. Thedelivery time estimate may include an estimate of the time required forthe selected UAV to travel to the source location, retrieve the item,travel to the delivery location and disengage the item. Likewise, if theroute includes a relay location, the time required for the UAV to travelto the relay location, switch power modules (or recharge) may beincluded in the delivery time estimate.

If the user has selected a delayed delivery time, the selected deliverytime may be used as the delivery time estimate. For example, if it isdetermined that an item can be aerially delivered within thirty minutes,the user may have the option to select a delayed aerial delivery timethat is longer than thirty minutes. In such an example, the UAV maydelay the initiation of the delivery of the item until the delivery willresult in the item being delivered at the requested delivery time.Likewise, in some implementations, the item may be partially delivered(e.g., to a relay location, secure delivery location) and remain thereuntil it is retrieved by a UAV and delivered to the user selecteddelivery location at the requested delivery time.

In addition to determining the delivery time estimate, deliveryparameters for the delivery of the item(s) may be generated and providedto the UAV. This may only be done when an item is ordered. The deliveryparameters may include, among other information, the identity of the UAVthat is to transport the ordered item(s) from the source location to thedelivery location, the weight, size and/or shape of the item, theidentification of the source location from which the item is to beretrieved, the destination location to where the item is to bedelivered, etc.

While the example of FIG. 8 only refers to a single UAV transporting theitem(s) from a source location to a delivery location, in someimplementations, multiple UAVs may be involved in delivery of an item.For example, a first UAV may transport the item from a source locationto a relay location. A second UAV may retrieve the item from the relaylocation and complete the delivery to the delivery location.

FIG. 9 is a flow diagram illustrating an example automated aerialdelivery process 900, according to an implementation. The exampleprocess 900 begins by a UAV receiving inventory information and adelivery location, as in 902. Inventory information may include, forexample, an identification of one or more items of inventory that are tobe delivered to a delivery location, a location of the inventory, alocation of a container that includes the inventory, etc. The deliverylocation may include location information for a delivery location forthe inventory. For example, the delivery location may be identified bylongitude and latitude information, GPS data, a physical address, etc.

Upon receiving inventory information and a delivery location, the UAVmay autonomously navigate to the physical location of the inventoryidentified in the inventory information, as in 904. For example, the UAVmay utilize its propellers and propeller motors to move aerially and anavigation system to navigate the UAV to the location of the inventory.Upon reaching the inventory location, the UAV may engage the inventoryusing the inventory engagement mechanism coupled to the UAV, as in 906.Upon engaging inventory, a determination may be made as to whether theinventory is securely engaged, as in 908. For example, one or more inputdevices on the UAV may be used to determine the position of theinventory in the inventory engagement mechanism. For example, the inputdevice may be a camera, pressure sensor, etc. that can be used todetermine the position of the inventory with respect to the inventoryengagement mechanism.

If it is determined that the inventory is not securely engaged, theexample process 900 returns to block 906 and continues until theinventory is securely engaged. If it is determined that the inventory issecurely engaged, the example process 900 develops a navigation pathfrom the current location to the delivery location. In someimplementations, the navigation path may be provided to the UAV. Inother implementations, the UAV may determine the navigation path. Instill other implementations, the navigation path may be determined basedon a combination of both provided information and navigation pathdeterminations made by the UAV. In still other examples, multiple UAVsmay communicate and share information, such as weather, dangerous areas,flight paths, etc., that may be used by the UAV to determine anavigation path.

Based on the determined navigation path, the UAV navigates to thedelivery destination, as in 910. Upon reaching the delivery destination,the UAV identifies a fairly level surface with a clear path to which theUAV can navigate and disengage the inventory for final delivery. A levelsurface may be, for example, a table, the ground, a chair, a balcony, orthe like. Upon identifying a level surface, the UAV positions itselfover the level surface and lowers itself such that it is hovering justabove the level surface. When the UAV reaches a desired position, theinventory is disengaged from the inventory engagement mechanism, as in912. Upon disengagement, the inventory exits the inventory engagementmechanism and comes to rest on the level surface. A determination may bemade as to whether the inventory has been fully released, as in 914. Forexample, the input devices on the UAV may be used to determine theposition of the inventory on the level surface and/or to confirm thatthere is no longer any inventory in the inventory engagement mechanism.If it is determined that the inventory has not been fully released, theexample process 900 returns to block 912 and continues until theinventory is released. Upon determining that the inventory has beenreleased from the inventory engagement mechanism, the example process900 completes, as in 916.

FIG. 10 is a flow diagram illustrating an example UAV route planningprocess 1000, according to an implementation. The example process 1000begins by receiving the delivery parameters, such as those created aspart of the example process 800, as in 1002. Based on the deliveryparameters, relevant environment information may be obtained from theUAV mesh network, such as the mesh network discussed above with respectto FIG. 5, as in 1004. For example, information regarding the weather,traffic, dangerous areas, etc. along a general path between the sourcelocation and a delivery location may be obtained from the UAV network.Based on the delivery parameters and the environmental conditionsobtained from the UAV network, a route from the current location of theUAV to the source location and from the source location to the deliverylocation is developed, as in 1006. For example, the UAV may be at aphysical location that is separate from the source location and thus,may be required to navigate to the source location to retrieve the itemthat is to be delivered. For example, if a third party has sold an itemthat is to be delivered by a UAV, the location of the item sold by thethird party may be the source location. In some implementations, theroute may only include route information (e.g., directions from thecurrent location to the source location and from the source location tothe destination location). In other implementations, the route may alsoinclude altitude, speed and/or other information about the route.

Once the route is determined, the UAV may begin following the route, asin 1008. As discussed in further detail below with respect to FIG. 11,the specific navigation of the route may be determined by the UAV duringtraversal of the route. As the route is followed, the status of the UAVmay be periodically reported to the UAV management system. For example,the position on the route, trajectory, speed, altitude, etc. may beperiodically reported to the UAV management system.

As the UAV traverses the route, the UAV may be in constant or periodiccommunication with other UAVs, the UAV management system, materialshandling facilities and/or relay locations, receiving and/or providingupdates regarding the environment and/or other information. Based onreceived and/or collected information, a determination may be made as towhether one or more environmental conditions have changed, as in 1010.If it is determined that an environmental condition has changed, theexample process 1000 returns to block 1006 and redevelops the route.However, if it is determined that the environment has not changed, theexample process 1000 determines if the destination location has changed,as in 1012. As discussed above, the destination location may dynamicallyupdate based on the activities of the user to which the item(s) is beingdelivered. For example, if the user has selected that the item bedelivered to their current location, the destination location may changeif the user moves to a new location while the item is being delivered.

If it is determined that the destination location has changed, theexample process 1000 returns to block 1006 and redevelops the route sothat it terminates at the new delivery location. However, if it isdetermined that the delivery location has not changed, a determinationis made as to whether the delivery of the item(s) has completed, as in1014. If it is determined that the delivery has not completed, theexample process 1000 returns to block 1008 and continues. If thedelivery has been completed, the example process completes and the UAVawaits additional instructions. In some implementations, if additionalinstructions are not provided, the UAV may automatically begin travelingback to the nearest relay location and/or materials handling facility.

FIG. 11 is a flow diagram illustrating an example route navigationprocess 1100, according to an implementation. The example process may beperformed by each UAV and be designed around a prime directive ofcausing no harm to humans or other animals. Generally, the UAV maynavigate a route such that the UAV, even if it completely loses controland/or power will not cause harm to humans or other animals. Forexample, the navigation of a route may be developed such that even ifthe UAV loses power it will not collide with a human or other animal.

The example route navigation process 1100 begins by determining thecurrent speed, altitude and/or trajectory of the UAV, as in 1102.Likewise, the surrounding environment of the UAV may be determined, asin 1104. For example, the UAV may utilize one or more inputs todetermine the surrounding environment and/or receive information fromother UAVs in the area. For example, time of flight sensors, sonar,cameras, etc. may be used to determine the surrounding environment. Inother implementations, stored maps and/or information about theenvironment surrounding the UAV may be accessed. Based on the determinedspeed, altitude, trajectory and surrounding environment, a failure pathis determined, as in 1106. A failure path may be the path the UAV wouldfollow if all power and control of the UAV was lost. For example, basedon the collected information, it may be determined where the UAV wouldland if all control and power were lost.

Based on the current path of the UAV and the determined failure path, adetermination is made as to whether the current navigation path and/orfailure path intersects with humans, other animals, roads, walkwaysand/or other areas that may be populated with humans and/or animals(e.g., houses, building, parks), as in 1108. If it is determined thatthe navigation path and/or failure path intersects with a human and/orother animals, roads, walkways, etc., the navigation path may be alteredto avoid the humans, animals, roads, walkways, etc., as in 1110. In someimplementations, the intersection can be completely avoided. In otherimplementations, potential interaction cannot be completely avoided. Insuch an instance, the navigation path will be altered to minimize anypotential interaction. For example, if the navigation path intersectswith a road, walkway or other human occupied path, the navigation pathmay be modified so that the intersection is limited (e.g., the UAV maycross the path at a perpendicular angle). As another example, thenavigation path may be developed to minimize any potential humaninteraction. For example, if the navigation path requires that the UAVtravel over and/or into a densely populated neighborhood, the navigationpath will be modified such that if the UAV loses all power and controlit will come to rest on a rooftop, in a tree, or another area that isnot frequented by humans.

If it is determined that the current navigation path does notpotentially intersect with humans and/or other animals, or if it hasalready been modified to reduce any such interaction, the exampleprocess 1100 returns to block 1102 and continues.

FIG. 12 is a flow diagram illustrating an example delivery notificationprocess 1200, according to an implementation. The example process 1200begins when a UAV departs a source location with an item(s) that is tobe delivered to a delivery location, as in 1202. When the UAV departsthe source location with the item(s) to be delivered, a notification isprovided to the user that ordered the item(s) and/or that is to receivethe item(s), as in 1204. For example, the user may receive an emailmessage, text message, instant message, phone call, or the like thatnotifies the user that the ordered item(s) has departed the sourcelocation and is in-route to the user selected delivery location. Themessage may also include an estimated delivery time.

Next, it is determined by the example delivery notification process 1200that the UAV is arriving at the delivery location, as in 1206. Forexample, when the UAV is within a defined distance (e.g., 1 mile) of thedelivery location, it may be determined that the UAV is arriving at thedelivery location. Upon determining that the UAV is arriving at thedelivery location, a notification may be provided to the user alertingthem that the ordered item(s) will soon be arriving, as in 1208. As withthe prior notification, the notification that the item will soon bearriving may be provided via email, text message, instant message, phonecall, or the like.

In addition to determining that the item will soon arrive at the userselected delivery location, a determination may be made as to whether arequest for placement of a remote entity controller is to be made, as in1210. For example, if the delivery is an attended delivery to a userselected location where a delivery has not been previously made, it maybe determined that a remote entity controller is to be placed at thedelivery location. As discussed above with respect to FIG. 6, a remoteentity controller may be, for example, a portable device of the user.

If it is determined that a request for placement of a remote entitycontroller is to be made, the request is provided to the user, as in1212. After requesting placement of the remote entity controller, thedelivery of the item is completed, as in 1214. If the remote entitycontroller is placed at the delivery location, the delivery may becompleted by providing control of the UAV to the remote entitycontroller, as discussed above. If the remote entity controller is notplaced at delivery location, or if it is determined that a request forplacement of a remote entity controller is not to be made or is notneeded, the example process 1200 may continue by determining a landingarea for landing the UAV and delivering the item(s), as in 1216. Forexample, if an item has previously been delivered to the deliverylocation, stored landing area information may be obtained from the UAVmanagement system and used to select a landing area for delivery of theitem. Alternatively, the UAV may use one or more inputs to determine alocation for delivery of the items. For example, the UAV may includeand/or use a camera, sonar, time of flight sensor, radar, etc. toanalyze the delivery location and select a landing area. Once thelanding area has been selected, the delivery is completed, as in 1218.In addition, once delivery is completed, a notification may be providedto the user that ordered the item(s) and/or the user that is to receivethe item(s) that the delivery of the item(s) has been completed, as in1220.

FIG. 13 is a flow diagram illustrating an example UAV landing process1300, according to an implementation. The example process 1300 beginswhen a UAV arrives at a source location, a delivery location and/or arelay location, as in 1302. As the UAV arrives at the location, alanding area is determined, as in 1304. As discussed above with respectto FIG. 12, the landing area may be determined based on a position of aremote entity controller, a prior landing at the area, etc.

In addition to determining the landing area, a determination may be madeas to whether the landing area and the path between the UAV and thelanding area are safe, as in 1306. For example, one or more inputs ofthe UAV and/or the remote entity controller may be used to obtaininformation (e.g., images) of the area. The obtained information may beprocessed to determine whether there are any humans, animals or otherobstacles in the landing area and/or the path between the UAV and thelanding area. Alternatively, or in addition thereto, the obtainedinformation may be provided to a remote entity, such as a user or theUAV management system, and the remote entity may verify that the landingarea is safe.

If it is determined that there are humans, animals or other obstacles,it may be determined that the landing area is not safe. If it isdetermined that the landing area is not safe, an alternate landing areaat the delivery location is determined, as in 1308. Upon selecting analternate landing area, the example process 1300 returns to decisionblock 1306 and continues.

If it is determined that the landing area and the path between the UAVand the landing area are safe, a determination is made as to whether acontrol request has been received by the UAV from a remote entitycontroller at the landing area, as in 1310. If it is determined that acontrol request has not been received, the UAV may complete anunattended landing at the delivery area, as in 1312. Alternatively, theUAV may not deliver the item. In another example, control of the UAV maybe provided to a remote entity (e.g., a user or the UAV managementsystem) and the remote entity may guide the UAV to the landing.

However, if it is determined that a control request has been received,control of the UAV is provided to the remote entity controller thatrequested control of the UAV, as in 1314. As discussed above, whencontrol is provided to the remote entity controller, the remote entitycontroller may capture images or other information about the UAV andprovide navigation instructions to the UAV to assist the UAV in landingat the landing area. Those instructions are received by the UAV andexecuted, as in 1316.

Once the UAV has landed or reached a desired height above the landingarea, a determination is made as to whether to engage or disengage anitem and/or container containing an item, as in 1318. For example, ifthe UAV is at a source location, it may be determined that the UAV is toengage an inventory item and/or a container that contains the inventoryitem. Engagement of items and containers is discussed above. Likewise,if the UAV already has an engaged inventory item(s) and/or a container,it may be determined that the UAV is to disengage the inventory item(s)or container. If it is determined that the UAV is to engage or disengagean inventory item(s) or a container, the UAV performs the determinedaction, as in 1320. However, if it is determined that the UAV is not toengage and/or disengage an item or container, the UAV may completelanding at the area, as in 1322. This may be done to recharge the UAV,so that repairs may be performed, to store the UAV, etc.

While the above examples have primarily discussed using theimplementations for the aerial transport of inventory to a user, inother implementations, the UAVs may be configured for other purposes.For example, in some implementations, the UAVs may be configured toretrieve and/or transport other UAVs. In such an example, the UAV(s)being transported are the inventory. Likewise, in some implementations,the inventory transported may be power modules, empty containers, andthe like. For example, a UAV may retrieve multiple power modules from asource location and transport those power modules to a delivery location(e.g., secure delivery location, a relay location) for use by otherUAVs. When the UAV is at the delivery location it may retrieve one ormore containers and transport those containers to another deliverylocation. In still other examples, UAVs may be used to transportinventory between materials handling facilities, between a third partymerchant and a materials handling facility, etc.

FIG. 14 is a block diagram illustrating an example UAV control system210 of the UAV 200. In various examples, the block diagram may beillustrative of one or more aspects of the UAV control system 210 thatmay be used to implement the various systems and methods discussedabove. In the illustrated implementation, the UAV control system 210includes one or more processors 1402, coupled to a non-transitorycomputer readable storage medium 1420 via an input/output (I/O)interface 1410. The UAV control system 210 may also include a propellermotor controller 1404, such as an electronic speed control (ESC), apower module 1406 and/or a navigation system 1408. The UAV controlsystem 210 further includes an inventory engagement mechanism controller1412, a network interface 1416, and one or more input/output devices1418.

In various implementations, the UAV control system 210 may be auniprocessor system including one processor 1402, or a multiprocessorsystem including several processors 1402 (e.g., two, four, eight, oranother suitable number). The processor(s) 1402 may be any suitableprocessor capable of executing instructions. For example, in variousimplementations, the processor(s) 1402 may be general-purpose orembedded processors implementing any of a variety of instruction setarchitectures (ISAs), such as the x86, PowerPC, SPARC, or MIPS ISAs, orany other suitable ISA. In multiprocessor systems, each processor(s)1402 may commonly, but not necessarily, implement the same ISA.

The non-transitory computer readable storage medium 1420 may beconfigured to store executable instructions, data, navigation pathsand/or data items accessible by the processor(s) 1402. In variousimplementations, the non-transitory computer readable storage medium1420 may be implemented using any suitable memory technology, such asstatic random access memory (SRAM), synchronous dynamic RAM (SDRAM),nonvolatile/Flash-type memory, or any other type of memory. In theillustrated implementation, program instructions and data implementingdesired functions, such as those described above, are shown storedwithin the non-transitory computer readable storage medium 1420 asprogram instructions 1422, data storage 1424 and navigation path data1426, respectively. In other implementations, program instructions, dataand/or navigation paths may be received, sent or stored upon differenttypes of computer-accessible media, such as non-transitory media, or onsimilar media separate from the non-transitory computer readable storagemedium 1420 or the UAV control system 210. Generally speaking, anon-transitory, computer readable storage medium may include storagemedia or memory media such as magnetic or optical media, e.g., disk orCD/DVD-ROM, coupled to the UAV control system 210 via the I/O interface1410. Program instructions and data stored via a non-transitory computerreadable medium may be transmitted by transmission media or signals suchas electrical, electromagnetic, or digital signals, which may beconveyed via a communication medium such as a network and/or a wirelesslink, such as may be implemented via the network interface 1416.

In one implementation, the I/O interface 1410 may be configured tocoordinate I/O traffic between the processor(s) 1402, the non-transitorycomputer readable storage medium 1420, and any peripheral devices, thenetwork interface 1410 or other peripheral interfaces, such asinput/output devices 1418. In some implementations, the I/O interface1410 may perform any necessary protocol, timing or other datatransformations to convert data signals from one component (e.g.,non-transitory computer readable storage medium 1420) into a formatsuitable for use by another component (e.g., processor(s) 1402). In someimplementations, the I/O interface 1410 may include support for devicesattached through various types of peripheral buses, such as a variant ofthe Peripheral Component Interconnect (PCI) bus standard or theUniversal Serial Bus (USB) standard, for example. In someimplementations, the function of the I/O interface 1410 may be splitinto two or more separate components, such as a north bridge and a southbridge, for example. Also, in some implementations, some or all of thefunctionality of the I/O interface 1410, such as an interface to thenon-transitory computer readable storage medium 1420, may beincorporated directly into the processor(s) 1402.

The propeller motor(s) controller 1404 communicates with the navigationsystem 1408 and adjusts the power of each propeller motor to guide theUAV along a determined navigation path to a delivery location. Thenavigation system 1408 may include a GPS or other similar system thancan be used to navigate the UAV to and/or from a delivery location. Theinventory engagement mechanism controller 1412 communicates with themotor(s) (e.g., a servo motor) used to engage and/or disengageinventory. For example, when the UAV is positioned over a level surfaceat a delivery location, the inventory engagement mechanism controller1412 may provide an instruction to a motor that controls the inventoryengagement mechanism to release the inventory.

The network interface 1416 may be configured to allow data to beexchanged between the UAV control system 210, other devices attached toa network, such as other computer systems, and/or with UAV controlsystems of other UAVs. For example, the network interface 1416 mayenable wireless communication between numerous UAVs that aretransporting inventory to various delivery destinations. In variousimplementations, the network interface 1416 may support communicationvia wireless general data networks, such as a Wi-Fi network. Forexample, the network interface 1416 may support communication viatelecommunications networks such as cellular communication networks,satellite networks, and the like.

Input/output devices 1418 may, in some implementations, include one ormore displays, image capture devices, thermal sensors, infrared sensors,time of flight sensors, accelerometers, pressure sensors, weathersensors, etc. Multiple input/output devices 1418 may be present andcontrolled by the UAV control system 210. One or more of these sensorsmay be utilized to assist in the landing as well as avoid obstaclesduring delivery and/or engagement of inventory. For example, utilizing alocation signal from the GPS receiver and one or more IR sensors, theUAV may safely land on a location designated by the user. The IR sensorsmay be used to provide real-time data to assist the UAV in avoidingmoving/movable obstacles.

As shown in FIG. 14, the memory 1420 may include program instructions1422 which may be configured to implement the example processes and/orsub-processes described above. The data storage 1424 may include variousdata stores for maintaining data items that may be provided fordetermining navigation paths, retrieving inventory, landing, identifyinga level surface for disengaging inventory, etc.

In various implementations, the parameter values and other dataillustrated herein as being included in one or more data stores may becombined with other information not described or may be partitioneddifferently into more, fewer, or different data structures. In someimplementations, data stores may be physically located in one memory ormay be distributed among two or more memories.

Those skilled in the art will appreciate that the UAV control system 210is merely illustrative and is not intended to limit the scope of thepresent disclosure. The UAV control system 210 may also be connected toother devices that are not illustrated, or instead may operate as astand-alone system. In addition, the functionality provided by theillustrated components may in some implementations be combined in fewercomponents or distributed in additional components. Similarly, in someimplementations, the functionality of some of the illustrated componentsmay not be provided and/or other additional functionality may beavailable.

Those skilled in the art will also appreciate that, while various itemsare illustrated as being stored in memory or storage while being used,these items or portions of them may be transferred between memory andother storage devices for purposes of memory management and dataintegrity. Alternatively, in other implementations, some or all of thesoftware components may execute in memory on another device andcommunicate with the illustrated UAV control system. Some or all of thesystem components or data structures may also be stored (e.g., asinstructions or structured data) on a non-transitory,computer-accessible medium or a portable article to be read by anappropriate drive, various examples of which are described above. Insome implementations, instructions stored on a computer-accessiblemedium separate from the UAV control system 210 may be transmitted tothe UAV control system 210 via transmission media or signals such aselectrical, electromagnetic, or digital signals, conveyed via acommunication medium such as a wireless network. Various implementationsmay further include receiving, sending or storing instructions and/ordata implemented in accordance with the foregoing description upon acomputer-accessible medium. Accordingly, the techniques described hereinmay be practiced with other UAV control system configurations.

FIG. 15 is a pictorial diagram of an illustrative implementation of aserver system, such as the server system 520, that may be used in theimplementations described herein. The server system 520 may include aprocessor 1500, such as one or more redundant processors, a videodisplay adapter 1502, a disk drive 1504, an input/output interface 1506,a network interface 1508, and a memory 1512. The processor 1500, thevideo display adapter 1502, the disk drive 1504, the input/outputinterface 1506, the network interface 1508, and the memory 1512 may becommunicatively coupled to each other by a communication bus 1510.

The video display adapter 1502 provides display signals to a localdisplay (not shown in FIG. 15) permitting an operator of the serversystem 520 to monitor and configure operation of the server system 520.The input/output interface 1506 likewise communicates with externalinput/output devices not shown in FIG. 15, such as a mouse, keyboard,scanner, or other input and output devices that can be operated by anoperator of the server system 520. The network interface 1508 includeshardware, software, or any combination thereof, to communicate withother computing devices. For example, the network interface 1508 may beconfigured to provide communications between the server system 520 andother computing devices, such as a UAV, materials handling facility,relay location and/or a secure delivery location, as shown in FIG. 5.

The memory 1512 generally comprises random access memory (RAM),read-only memory (ROM), flash memory, and/or other volatile or permanentmemory. The memory 1512 is shown storing an operating system 1514 forcontrolling the operation of the server system 520. A binaryinput/output system (BIOS) 1516 for controlling the low-level operationof the server system 520 is also stored in the memory 1512.

The memory 1512 additionally stores program code and data for providingnetwork services to the UAV management system 526. Accordingly, thememory 1512 may store a browser application 1518. The browserapplication 1518 comprises computer executable instructions that, whenexecuted by the processor 1500, generate or otherwise obtainconfigurable markup documents such as Web pages. The browser application1518 communicates with a data store manager application 1520 tofacilitate data exchange between the inventory data store 1522, the userdata store 1524, and/or secure delivery location data store 1526, and/orother data stores.

As used herein, the term “data store” refers to any device orcombination of devices capable of storing, accessing and retrievingdata, which may include any combination and number of data servers,databases, data storage devices and data storage media, in any standard,distributed or clustered environment. The server system 520 can includeany appropriate hardware and software for integrating with the datastores 1522-1526 as needed to execute aspects of one or moreapplications for the UAV management system, UAVs, materials handlingfacilities, secure delivery locations, and/or relay locations

The data stores 1522-1526 can include several separate data tables,databases or other data storage mechanisms and media for storing datarelating to a particular aspect. For example, the data stores 1522-1526illustrated include mechanisms for inventory information, containerinformation, UAV information, user information, weather information,route information, source location information, delivery locationinformation, etc., which can be used to generate and deliver informationto the UAV management system 526, materials handling facilities, securedelivery locations, UAVs, relay locations, and/or users.

It should be understood that there can be many other aspects that may bestored in the data stores 1522-1526. The data stores 1522-1526 areoperable, through logic associated therewith, to receive instructionsfrom the server system 520 and obtain, update or otherwise process datain response thereto.

The memory 1512 may also include the UAV management system 526,discussed above. The UAV management system 526 may be executable by theprocessor 1500 to implement one or more of the functions of the serversystem 520. In one implementation, the UAV management system 526 mayrepresent instructions embodied in one or more software programs storedin the memory 1512. In another implementation, the UAV management system526 can represent hardware, software instructions, or a combinationthereof.

The server system 520, in one implementation, is a distributedenvironment utilizing several computer systems and components that areinterconnected via communication links, using one or more computernetworks or direct connections. However, it will be appreciated by thoseof ordinary skill in the art that such a system could operate equallywell in a system having fewer or a greater number of components than areillustrated in FIG. 15. Thus, the depiction in FIG. 15 should be takenas being illustrative in nature and not limiting to the scope of thedisclosure.

Those skilled in the art will appreciate that in some implementationsthe functionality provided by the processes and systems discussed abovemay be provided in alternative ways, such as being split among moresoftware modules or routines or consolidated into fewer modules orroutines. Similarly, in some implementations, illustrated processes andsystems may provide more or less functionality than is described, suchas when other illustrated processes instead lack or include suchfunctionality respectively, or when the amount of functionality that isprovided is altered. In addition, while various operations may beillustrated as being performed in a particular manner (e.g., in serialor in parallel) and/or in a particular order, those skilled in the artwill appreciate that in other implementations the operations may beperformed in other orders and in other manners. Those skilled in the artwill also appreciate that the data structures discussed above may bestructured in different manners, such as by having a single datastructure split into multiple data structures or by having multiple datastructures consolidated into a single data structure. Similarly, in someimplementations, illustrated data structures may store more or lessinformation than is described, such as when other illustrated datastructures instead lack or include such information respectively, orwhen the amount or types of information that is stored is altered. Thevarious methods and systems as illustrated in the figures and describedherein represent example implementations. The methods and systems may beimplemented in software, hardware, or a combination thereof in otherimplementations. Similarly, the order of any method may be changed andvarious elements may be added, reordered, combined, omitted, modified,etc., in other implementations.

From the foregoing, it will be appreciated that, although specificimplementations have been described herein for purposes of illustration,various modifications may be made without deviating from the spirit andscope of the appended claims and the elements recited therein. Inaddition, while certain aspects are presented below in certain claimforms, the inventors contemplate the various aspects in any availableclaim form. For example, while only some aspects may currently berecited as being embodied in a computer readable storage medium, otheraspects may likewise be so embodied. Various modifications and changesmay be made as would be obvious to a person skilled in the art havingthe benefit of this disclosure. It is intended to embrace all suchmodifications and changes and, accordingly, the above description to beregarded in an illustrative rather than a restrictive sense.

1-20. (canceled)
 21. A system for aerial delivery of items to a destination location, comprising: a plurality of aerial vehicles, each of the plurality of aerial vehicles configured to aerially transport items; an aerial vehicle management system, including: a processor; and a memory coupled to the processor and storing program instructions that when executed by the processor cause the processors to at least: receive from a device a request to order an item for aerial delivery, the item available through an e-commerce shopping site; and send to an aerial vehicle of the plurality of aerial vehicles, delivery parameters identifying at least a destination location; wherein the aerial vehicle, in response to receiving the delivery parameters, is further configured to at least: aerially navigate to the destination location with the item; and disengage the item at the destination location.
 22. The system of claim 21, wherein the aerial vehicle is further configured to at least: receive environment information; and develop a navigation route to the destination location based at least in part on the delivery parameters and the environment information.
 23. The system of claim 21, wherein the destination location is at least one of a secure delivery location, a device location, a user designated delivery location, or a relay location.
 24. The system of claim 21, wherein the program instructions that when executed by the processor further cause the processor to at least: determine, based at least in part on the request, a delivery time estimate identifying an estimated amount of time required to transport the item to the destination location.
 25. The system of claim 21, wherein the aerial vehicle, in response to receiving the delivery parameters, is further configured to at least: determine, at the destination location, a surface; aerially navigate, prior to disengagement of the item, to a position over the surface; and wherein the item is disengaged onto the surface.
 26. The system of claim 25, wherein the surface is at least one of a table, a ground, a chair, or a balcony.
 27. A computer-implemented method, comprising: under control of one or more computing systems configured with executable instructions, receiving at an e-commerce shopping site, a request to view information about an item; determining a potential delivery location for delivery of the item; determining a delivery time estimate for aerial delivery of the item to the potential delivery location; and providing for presentation by the e-commerce shopping site, the delivery time estimate.
 28. The computer-implemented method of claim 27, wherein the potential delivery location is determined based at least in part on one or more of a defined delivery location associated with a user account of a user that is accessing an e-commerce shopping site, or a current location of a device associated with the user.
 29. The computer-implemented method of claim 27, further comprising: receiving from the e-commerce shopping site, a request for delivery of the item to a delivery location; determine an aerial vehicle for delivery of the item; and send instructions that cause the aerial vehicle to aerially transport the item to the delivery location.
 30. The computer-implemented method of claim 29, further comprising: estimating a power requirement for autonomously delivering the item based at least in part on one or more of an aerial vehicle, the delivery location, a source location, a weight of the item, a size of the item, a distance between the source location and the delivery location, weather between the source location and the delivery location, a monetary value of the item, or the item.
 31. The computer-implemented method of claim 27, further comprising: receiving a request for delivery of the item to a delivery location; causing a first aerial vehicle to transport the item from a source location to a relay location; and causing a second aerial vehicle to transport the item from the relay location to the delivery location.
 32. The computer-implemented method of claim 27, further comprising: receiving a request for delivery of the item to a delivery location; determining a power requirement for aerial transport of the item to the delivery location; determining a first power module that will provide an aerial vehicle sufficient power to aerially transport the item from a source location to a relay location; and determining a second power module that will provide the aerial vehicle sufficient power to aerially transport the item from the relay location to the delivery location.
 33. The computer-implemented method of claim 27, wherein the potential delivery location is a secure delivery location configured to receive and store at least one item delivered by an aerial vehicle.
 34. The computer-implemented method of claim 27, further comprising: receiving a request that the item be delivered to a delivery location; determining that an aerial vehicle has departed with the item toward the delivery location; and sending a notification that the item is in-route to the delivery location.
 35. A system for aerial transport of items using aerial vehicles, comprising: an e-commerce shopping site configured to at least: provide item information to a user, the item information including a delivery option for aerial transport of an item to a delivery location; and receive a request for aerial delivery of the item to the delivery location; an aerial vehicle management systems configured to at least: wirelessly communicate with an aerial vehicle; and send delivery parameters to the aerial vehicle, the delivery parameters indicating at least the delivery location; the aerial vehicle configured to at least: wirelessly communicate with the aerial vehicle management system; receive the delivery parameters; receive the item; aerially navigate with the item to the delivery location; and disengage the item at the delivery location.
 36. The system of claim 35, wherein the aerial vehicle is further configured to at least determine a navigation path for aerial transport of the item to the delivery location.
 37. The system of claim 36, wherein the navigation path is determined based at least in part on one or more of delivery parameters provided by the aerial vehicle management system, environmental information, or information received from a second unmanned aerial vehicle.
 38. The system of claim 36, wherein the aerial vehicle is further configured to at least: determine a surrounding environment; and alter a navigation path, during aerial transport of the item, based at least in part on the navigation path.
 39. The system of claim 35, wherein the aerial vehicle management system is further configured to at least: send to a user a notification that the item is at least one of in-route to the delivery location or delivered to the delivery location.
 40. The system of claim 35, further comprising: a secure delivery location configured to receive an item delivered by the aerial vehicle. 